Studying on your own?

It’s not a secret that studying a certain carrier without attending any University it’s a hard work, we all know that, and as someone who’s currently studying programming and computer science by her own, I decided to write a post to share what I’ve experienced until now, what kind of obstacles you can encounter, and my personal advises of how to do it.

(more…)

PyConES 2015

I know, we are already in 2016 and I’m very slow at  publishing blog posts, but I didn’t want to skip this one. I realized it’s a great thing to share the conferences I attend and my experiences in each one of them; which bring us to talk about PyConES.

This PyconES was held in Valencia. It was a three days conference, in my opinion, totally worth it. It was really well organized. The first day was organized for all the workshops. I slipped in the Django Girls workshop and helped some of the attendants. It was really fun because I knew one of the organizers and also some of the attendants, so that made it even more fun that it normally is.

I learned new things in the following two days. There where lots of great talks, some of them where really scientific, but amazingly interesting at the same time. Other talks helped me clear some of my doubts and understand things better, they were really useful.

I found many of the talks really original and exciting, but what I liked the most were the keynotes, in particular I found really inspiring one held by Yamila Moreno about what can the Python community learn from Plutarch, and about how embracing the diversity in the Python community can help one day to improve the entire society (I’ll  upload this keynote for the Spanish speakers as soon it’s available).

In general it was a great conference that I hoped it lasted a little longer than just three days, it was really refreshing and awesome for a beginner developer. As I said before, it was totally worth it. Absolutely not to miss if you speak or understand Spanish.

 

Thank you Outreachy!

Hello!

This week was my last week in the Outreachy internship and, now that it’s over, I would like to share with you what I have to say about my whole experience.

Even if I had worked before in the OpenStack Zaqar project, during this internship I could get more deeply into it and understand it better. I have to say that at first, it was kinda hard to totally understand everything, and sometimes I felt like a fish out of the water, but the more I went on and the more I was able to get more familiar with everything. (more…)

Implementing missing endpoints

Hello people!

I’d like to share with you my weekly internship experience. This week I had the opportunity to finally start digging into the code! So at first, I had to understand how was the API organized. Once I understood that, I started working on the code by adding the features that were missing, which were:  ‘pool_update’, ‘pool_list’, ‘flavor_update’ and a ‘flavor_list’. There were other methods that had a similar functionality, so I could use those to implement something like that in the missing endpoints I was working on.

After writing code for these features, I started working on unit tests; as some of the methods I could look at in order to implement the missing endpoints, there were also some tests that I could use as examples to write my tests, even though I had some trouble understanding how to implement the flavor_update test. Flavors and pools usually have a similar implementation, but they are different from each other: you can think about pools like containers, or more precisely, like containers of data containers; while flavors basically have the main task of exposing pools.

(more…)

Dealing with specs

Hello everyone!

So, as I said before, I got accepted to Outreachy and my whole task during my internship  is to work for OpenStack on python-zaqarclient adding support for Zaqar API v1.1. This week, I had to work on a specification that explained what features are missing in the client side of Zaqar, and which are the things that need to be done in order to add those features.

The thing about specs is that they have to be written with the markup language, which is a system for annotating a document in a way that is syntactically distinguishable from the text. Python uses a type of markup language for documentation, called reStructuredText, which is a component of Docutils.

When writing a spec you have to be very careful to the syntax, because writing something syntactically wrong, changes completely the output, and you’ll have to fix it in order to see your spec like it should be seen. Here’s a link to the reStructuredText, if you want to know more about it: http://docutils.sourceforge.net/docs/user/rst/quickref.html.

Anyway, working on specs was my first weakly internship experience, and I found out that you need to be very precise and be careful to the way you write them, but people is always open to help you understand what is wrong or what you could improve. It was also great to know that my mentor was always available and ready to help me if I had any kind of question.

So, that’s it! Be ready for my next posts because they’ll become more interesting every week!